Mobility detection for edge applications in wireless communication networks

ABSTRACT

Various embodiments detecting wireless communication device mobility in a wireless communication network. In one embodiment, one or more Internet Protocol (IP) data packets associated with a wireless communication device are analyzed. The wireless communication device is coupled with the edge entity. A determination is made, based on the analyzing, that the wireless communication device is a newly coupled device at the edge entity. A central entity disposed within the wireless communication network is notified that the wireless communication device is currently coupled to the edge entity.

BACKGROUND

The present invention generally relates to wireless communicationnetworks, and more particularly relates to user equipment mobilitydetection in wireless communication networks.

Demand for wireless services is increasing rapidly as evident by thetremendous growth in recent years in smart mobile phones. This explosivegrowth in data traffic and its bandwidth requirements have alreadysaturated the current generation of cellular networks and will continueto pose a major bandwidth challenge for next generation of cellularnetworks (e.g., Long Term Evolution (LTE) based networks). Thus, whileLTE networks will have greater capacity than current networks, they willcarry significantly larger data traffic over both the radio and thebackhaul links.

BRIEF SUMMARY

In one embodiment, a method, with an edge entity disposed at an edge ofa wireless communication network, for detecting mobility of wirelesscommunication devices is disclosed. The method comprises analyzing oneor more Internet Protocol (IP) data packets associated with a wirelesscommunication device, wherein the wireless communication device iscoupled with the edge entity. A determination is made, based on theanalyzing, that the wireless communication device is a newly coupleddevice at the edge entity. A central entity disposed within the wirelesscommunication network is notified, based on the determination, that thewireless communication device is currently coupled to the edge entity.

In another embodiment, a method, with an edge entity disposed at an edgeof a wireless communication network, for detecting mobility of wirelesscommunication devices is disclosed. The method comprises monitoring forInternet Protocol (IP) data packets associated with a given wirelesscommunication device. A determination is made that one or more IP datapackets associated with the given wireless communication device havefailed to be received within a given threshold. A set of wirelesscommunication device location information associated with the givenwireless communication device is updated, based on the determination, toindicate that the given wireless communication device has been decoupledfrom the edge entity.

In another embodiment, a method, with a central entity disposed within awireless communication network, for detecting mobility of wirelesscommunication devices is disclosed. The method comprises interceptingone or more Internet Protocol (IP) data packets associated with awireless communication device, wherein the wireless communication deviceis coupled to an edge entity. A determination is made that the one ormore IP data packets have been changed by the edge entity. At least oneidentifier associated with the edge entity is identified within the oneor more IP data packets based on the determination. A set of wirelesscommunication device location information is updated based on the atleast one identifier to indicate that the wireless communication deviceis currently coupled to the edge entity.

In another embodiment, a method, with a central entity disposed within awireless communication network, for detecting mobility of wirelesscommunication devices is disclosed. The method comprises interceptingone or more Internet Protocol (IP) data packets associated with awireless communication device. At least one parameter of the one or moreIP data packets is changed. An IP address associated with the wirelesscommunication device is identified. The one or more IP data packets thathave been changed are sent to the wireless communication device based onthe identified IP address.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The accompanying figures where like reference numerals refer toidentical or functionally similar elements throughout the separateviews, and which together with the detailed description below areincorporated in and form part of the specification, serve to furtherillustrate various embodiments and to explain various principles andadvantages all in accordance with the present invention, in which:

FIG. 1 is a block diagram illustrating one example of an operatingenvironment according to one embodiment of the present invention;

FIG. 2 is a block diagram illustrating a detailed view of a local UE(user equipment) device location manager according to one embodiment ofthe present invention;

FIG. 3 is a block diagram illustrating a detailed view of a global UEdevice location manager according to one embodiment of the presentinvention;

FIG. 4 shows one example of an environment for detecting UE devicemobility in a wireless communication network according to one embodimentof the present invention;

FIG. 5 shows one example of local UE location information according toone embodiment of the present invention;

FIG. 6 shows one example of updating the local UE location informationof FIG. 5 according to one embodiment of the present invention;

FIG. 7 shows one example of global UE location information according toone embodiment of the present invention;

FIG. 8 shows one example of updating the global UE location informationof FIG. 7 according to one embodiment of the present invention;

FIG. 9 shows another example of updating the global UE locationinformation of FIG. 7 according to one embodiment of the presentinvention;

FIG. 10 shows another example of an environment for detecting UE devicemobility in a wireless communication network according to one embodimentof the present invention;

FIG. 11 shows one example of an IP (Internet Protocol) data packet thathas been changed for detection of UE device mobility according to oneembodiment of the present invention;

FIG. 12 is an operational flow diagram illustrating one example ofdetecting mobility of UE devices by an edge entity in a wirelesscommunication network according to one embodiment of the presentinvention;

FIG. 13 is an operational flow diagram illustrating another example ofdetecting mobility of UE devices by an edge entity in a wirelesscommunication network according to one embodiment of the presentinvention;

FIG. 14 is an operational flow diagram illustrating one example ofdetecting mobility of UE devices by a central entity in a wirelesscommunication network according to one embodiment of the presentinvention;

FIG. 15 is an operational flow diagram illustrating another example ofdetecting mobility of UE devices by an central entity in a wirelesscommunication network according to one embodiment of the presentinvention; and

FIG. 16 is a block diagram illustrating one example of an informationprocessing system according to one embodiment of the present invention.

DETAILED DESCRIPTION

Data traffic management is becoming more important for network operatorsas they try to curb the amount of data traffic that traverses thebackhaul and core networks in the cellular network infrastructure. Oneoption for reducing data traffic at the backhaul and core networks is todeploy applications and serve the wireless mobile users' data/servicerequests at the edge of the wireless networks (e.g., at the basestation). Most of the application and appliances built on top of TCP/IPprotocol stacks assume that the locations of the users are fixed orslowly changing. However, this assumption does not hold true when theseapplications are deployed at the edge of the wireless networks. Thesignificance of this mismatch in the assumption on the user location (ormobility) is that, often, the edge applications cannot adequately servethe mobile users when the users' locations change during the applicationsession.

A challenging problem in handling the user mobility for the edgeapplications is to detect the current location of the mobile users,i.e., which edge node a particular user is currently connected to usinginformation available in the TCP/IP layer. The existence of multiplelayers between the TCP/IP protocols and the cellular network protocolsthat handle the mobility makes it difficult to expose the users' currentlocation information to the TCP/IP applications in a generic manner.

Therefore, one or more embodiments utilize the information available atthe TCP/IP protocol suites to detect the current location of mobileusers in a wireless communication network. In one embodiment, this isaccomplished by using a combination of devices located at the edge andat the core. For example, one or more edge entities (EEs) areimplemented at the edge of the wireless communication networks and acentral entity (CE) is implemented at the gateway location in thenetwork. The CE and EEs work in coordination to detect where aparticular user is currently located within the network.

Operating Environment

FIG. 1 shows an operating environment 100 according to one embodiment ofthe present invention. The operating environment 100 comprises one ormore wireless communication networks 102 that are communicativelycoupled to one or more wire line networks 104. For purposes ofsimplicity, only the portions of these networks that are relevant toembodiments of the present invention are described. The wire linenetwork 104 acts as a back-end for the wireless communication network102. In this embodiment, the wire line network 104 comprises one or moreaccess/core networks of the wireless communication network 102 and oneor more Internet Protocol (IP) networks such as the Internet. The wireline network 104 communicatively couples, for example, one or morecontent sources/providers, such as a server(s) 106, to the wirelesscommunication network 102. In further embodiments, the back-end is not awire line network. For example, in one embodiment the back-end is awireless network and takes the form of a point-to-point back-end networksuch as a directional microwave network used to transmit and receivesignals bi-directionally. Alternatively, the back-end takes the form ofa network of peers in which a mobile base station (e.g., eNodeB in thecase of GSM and its descendants) is itself used as a back-end networkfor other base stations.

The wireless communication network 102 supports any wirelesscommunication standard such as, but not limited to, Global System forMobile Communications (GSM), Code Division Multiple Access (CDMA), TimeDivision Multiple Access (TDMA), General Packet Radio Service (GPRS),Frequency Division Multiple Access (FDMA), Orthogonal Frequency DivisionMultiplexing (OFDM), or the like. The wireless communication network 102includes one or more networks based on such standards. For example, inone embodiment, the wireless communication network 102 comprises one ormore of a Long Term Evolution (LTE) network, an Evolution Data Only(EV-DO) network, a GPRS network, a Universal Mobile TelecommunicationsSystem (UMTS) network, and the like. In the example of FIG. 1, thewireless communication network 102 is an LTE network.

FIG. 1 further shows that one or more user devices (also referred toherein as “user equipment (UE)”) 108, 110 are communicatively coupled tothe wireless communication network 102. The UE devices 108, 110, in thisembodiment, are wireless communication devices such as two-way radios,cellular telephones, mobile phones, smartphones, two-way pagers,wireless messaging devices, laptop computers, tablet computers, desktopcomputers, personal digital assistants, and other similar devices. UEdevices 108, 110 access the wireless communication network 102 throughone or transceiver nodes 112, 114 situated at the edge of the wirelesscommunication network 102. For example, the UE devices 108, 110 accessthe wireless communication network 102 through one or more transceivernodes 112, 114 using one or more air interfaces 115 established betweenthe UE devices 108, 110 and the transceiver nodes 112, 114.

In another embodiment, one or more UE devices 108, 110 access thewireless communication network 102 via a wired network and/or anon-cellular wireless network such as, but not limited to, a WirelessFidelity (WiFi) network. For example, the UE devices 108, 110 can becommunicatively coupled to one or more gateway devices via wired and/orwireless mechanisms that communicatively couples the UE devices 108, 110to the wireless communication network 102. This gateway device(s), inthis embodiment, communicates with the wireless communication network102 via wired and/or wireless communication mechanisms.

The UE devices 108, 110 interact with the wireless communication network102 to send/receive voice and data communications to/from the wirelesscommunication network 104. For example, the UE devices 108, 110 are ableto wirelessly request and receive content (e.g., audio, video, text, webpages, etc.) from a provider, such as the server 106, through thewireless communication network 102. The requested content/service isdelivered to the wireless communication network 102 through the wireline network 104.

A transceiver node 112, 114 is known as a base transceiver station(BTS), a Node B, and/or an Evolved Node B (eNodeB) depending on thetechnology being implemented within the wireless communication network104. This exemplary embodiment relates to an LTE network, so theillustrated transceiver nodes 112, 114 are eNodeBs. The transceivernodes 112, 114 are communicatively coupled to one or more antennascommunicates directly with the core of the wireless communicationnetwork 102. It should be noted that in another embodiment, a radionetwork controller (RNC) or base station controller (BSC) iscommunicatively coupled to a transceiver node 112, 114 for managing andcontrolling one or more base stations.

In the example shown in FIG. 1 one or more mobility management entitiesand serving gateway nodes (MME/S-GW) 116 are communicatively coupled tothe plurality of eNodeBs 112, 114. A packet gateway node (P-GW) 118 iscommunicatively coupled to the MME/S-GW 116 and to the wire line network104 (e.g., Core IP Network). It should be noted that even though FIG. 1shows the MME combined with the S-GW, the MME can be separate anddistinct from the S-GW. It should be noted that the MME/S-GW is alsoreferred to herein as the “MME 116”. The MME/S-GW 116 manages mobility(e.g., a transfer) of the UE devices across different eNodeBs and alsoacts as a serving gateway for data. The P-GW 118 acts as the gateway tothe wire line network 104.

In one embodiment, the P-GW 124 performs bookkeeping operations such asgenerating charging data records (also referred to as call detailrecords) and data or voice interception. It should be noted thatbookkeeping operations can also be performed in or distributed acrossvarious other components of the wireless communication network 102 suchas the MME or S-GW.

In one example, the communication protocols between the UE devices 108,110 and the P-GW 118 are various 3rd Generation Partnership Project(3GPP) protocols over which the internet protocol (IP) traffic from theUE devices 108, 110 is tunneled. For example, a GPRS tunneling protocol(GTP) is utilized between the eNodeBs 112, 114 and the MME/S-GW 116 aswell as between the MME/S-GW 116 and the P-GW 118. A standard InternetProtocol (IP) is utilized between the P-GW 118 and the wire line network104. The server(s) 106 has a TCP (Transmission Control Protocol) socketthat communicates with a TCP socket at the UE devices 108, 110 when auser wishes to access data from the server 106. An IP tunnel is createdfrom the P-GW 118 to UE devices 108, 110 for user traffic and passesthrough the interim components, such as the MME/S-GW 116.

FIG. 1 further shows that at least one of the eNodeBs 112, 114 and theP-GW 118 are each communicatively coupled to a UE location manager 120,122. For example, at least one of the eNodeBs 112, 114 is coupled to alocal UE location manager 120 and the P-GW 116 is coupled to a global UElocation manager 122. In one embodiment, the local UE locationmanager(s) 120 resides within an information processing system referredto herein as an “edge entity (EE) 124” that is communicatively coupledto one or more eNodeBs 112. In one embodiment, the EE 124 is the same as(or is part of) the eNodeB 112. In this embodiment, the local UElocation manager 124 resides within the eNodeB 112. In anotherembodiment, the EE 124 is separate and distinct from the eNodeB 112. Theglobal UE location manager 122, in one embodiment, resides within theP-GW 118 (or alternatively the MME or the S-GW). In another embodiment,the global UE location manager 122 resides within a separate informationprocessing system that is communicatively coupled to the P-GW 118. Thesystem in which the global UE location manager 122 resides is hereinreferred to as a “central entity (CE)”. One example of an EE 124 is abyte caching system as discussed in the commonly owned U.S. patentapplication Ser. No. 13/601,306 entitled “Byte Caching In WirelessCommunication Networks” filed on Aug. 31, 2012, the entire disclosure ofwhich is hereby incorporated by reference in its entirety.

As will be discussed in greater detail below, the UE location managers120, 122 detect the current location/mobility of UE devices 108, 110 inthe wireless communication network 102 using the information availableat the TCP/IP protocol suites. Location/mobility refers to the currentEE 124 (and/or eNodeB 112, 114) coupled to a given UE device 108. Aswill be discussed in greater detail below, the local and global locationmanagers 120, 122 (and hence the CE 118 and the EEs 124) separatelymaintain UE location information comprising the current location of theUE devices 108, 110. The EEs 124 and CE 118 share this locationinformation through certain message exchanges. In one embodiment, an EE124 detects the arrival of a UE device 108 at its location by observingthe arrival of a new IP flow. The UE device 108 “arrives” at an EE 124when the UE device 108 is coupled to an eNodeB 112 associated with theEE 124. The CE 118 detects the coupling of a UE device 108 to an EE 124either by receiving an explicit notification from that EE 124 or byobserving one or more uplink packets that is mangled (changed) by thatEE 124.

An EE 124 detects the departure of a user from its location by receivinga notification from the CE 118 indicating the arrival of the same userat the location of some other EE. The EE 124 departs from an EE 124 whenit decouples from the eNodeB 112 associated with the EE 124. In anotherembodiment, an EE 124 detects the departure of a UE device 108 from itslocation by observing the lack of IP packets from/to the same UE devices108 at its location. The CE 118 detects the departure of a UE device 108from the location of an EE 124 either by (1) receiving an explicitnotification from the EE 124, which detected the departure implicitly;(2) receiving an explicit notification from some other EE that detectedthe arrival of the same UE device 108; or (3) observing certain patternsof the responses from the UE device 108 in response to the packetmangled by the CE 118.

FIGS. 2 and 3 show a more detailed example of the local UE locationmanager 120 and the global UE location manager 122, respectively. Inparticular, FIG. 2 shows that the local UE location manager 120 of an EE124 comprises a data packet analyzer 202, a comparator 204, an updater206, a CE notifier 208, a packet mangler 210, and a packet demangler212. FIG. 2 further shows that local UE location (mobility) information214 is also included within the EE 124 and/or the local UE locationmanager 120. The local UE location information 214 (also referred toherein as “local information 214”) is used by the local UE locationmanager 120 to record and maintain information associated with UEdevices 108, 110 that are currently coupled to the EE 124 (and/or eNodeB 112) associated with the local UE location manager 120. The local UElocation manager 120 and its components are discussed in greater detailbelow.

FIG. 3 shows that the global UE location manager 122 of the CE 118comprises a data packet analyzer 302, an updater 304, an EE notifier306, a packet mangler 308, and a packet demangler 310, and a UE feedbackanalyzer 312. FIG. 3 further shows that global UE location (mobility)information 314 is also included within the CE 118 and/or the global UElocation manager 122. The global UE location information 314 (alsoreferred to herein as “global information 314”) is used by the global UElocation manager 122 to record and maintain UE location information foreach EE 124 (and/or eNodeBs 112, 114) that is coupled to the CE 118. Theglobal UE location manager 122 and its components are discussed ingreater detail below.

Mobility Detection

The following is a more detailed discussion on detecting the currentlocation/mobility of UE devices 108, 110 in the wireless communicationnetwork 102 using the information available at the TCP/IP protocolsuites. FIG. 4 shows one embodiment, where a UE device 408 is coupled toan EE 425 by establishing a connection with an eNodeB 413 associatedwith the EE 425. A UE device 408 can be coupled to an EE 424 when thedevice enters the network 102 and connects to an eNodeB 412; moves fromone eNodeB 412 associated with an EE 424 to another eNodeB 413associated with another EE 425; etc.

In the example of FIG. 4 the UE device 408 attaches to the wirelesscommunications network in a conventional manner, and can then connect toany server (e.g., 406) from the Internet. For example, the UE device 108makes a TCP connection to a port (e.g., port 80) at a server 406 itwishes to receive data from. The packet analyzer 202 at the EE 425analyzes the IP data packets flowing through the IP tunnel Based on thisanalysis the packet analyzer 202 identifies the UE device 408 associatedwith the data packets. For example, the packet analyzer 202 identifiesthe source and/or destination addresses in each data packet receivedfrom the UE device 408 and/or server 406. If the data packet wasreceived from the UE side, the packet analyzer 202 extracts the sourceaddress from the packet. If the data packet was received from the serverside, the packet analyzer 202 extracts the destination address of datapacket. Alternatively, the packet analyzer 202 can analyze the signalingtraffic between the eNodeB 412 and the MME/S-GW 116 and/or CE (e.g.,P-GW) 418. The packet analyzer 202, based on this analysis, identifiesUE mobility events, such as (but not limited to) a new bindingassociation between a UE and an eNodeB or a disassociation between a UEand eNodeB. For example the packet analyzer 202 can analyze the proxymobile IP signaling traffic generated by an eNodeB and identify theaddress of the UE that has been associated or disassociated from theeNodeB.

Once the address associated with the UE device 408 has been identifiedand extracted the comparator 204 compares the address/ID to the localinformation 214. FIG. 5 shows one example of this information beingmaintained in a table 500 of a database. However, other mechanisms forstoring and organizing the local information 214 are applicable as well.In particular, the local information 214 comprises the IP address 502associated with each UE device 408 currently coupled to the EE 425. Thelocal information 214 can also comprise a unique ID 504 such as (but notlimited to) the electronic serial number (ESN) of the UE device 408. Itshould be noted that the local information 214 can also include otherinformation as well and is not limited to the examples shown in FIG. 5.

The comparator 204 compares the source/destination address (and/orunique ID) extracted from the received IP data packet(s) to the localinformation 214 to determine if the UE device 408 is a newly coupleddevice at the EE 425. For example, in the current example the UE device408 has an IP address of IP_ADDRESS_2. Therefore, the comparator 204analyzes the local information 214 to determine if an entry/recordexists for a UE device with IP_ADDRESS_2. In this example, an entrycomprising IP_ADDRESS_2 does not exist in the local information 214, asshown in FIG. 5. Therefore, the comparator 204 determines that the UEdevice 408 is a newly coupled device. The updater 206 adds an entry 602to the location information 214 comprising the IP address (e.g.,IP_ADDRESS_2) of the device 408, as shown in FIG. 6. Also, if a uniqueidentifier of the UE device 408 has also been extracted from the datapacket(s) this identifier is also added to the location information.Alternatively, the local UE location manager 120 can assign a unique IDto the UE device 408 as well.

The CE notifier 208 notifies the CE 418 that this particular UE device408 is currently located at (coupled to) the EE 425 (and/or eNodeB 413).For example, the CE notifier 208 sends a message to the CE 418comprising a unique identifier of the EE 425 (and/or eNodeB 414) as wellas the IP address and/or unique ID of the UE device 408. It should benoted that the EE 425 and CE 418 can use any TCP/IP based protocol toexchange messages. For example, the protocol messages can be encoded ina binary format by using remote procedure calls, or a human readableformat by using web services. The updater 304 at the CE 418 updates theglobal information 314 based on this UE location information receivedfrom the EE 424.

In one embodiment, the global information 314 comprises the locationinformation of each UE device 408 coupled to an EE 424, 425 (and/oreNodeB 412, 414) associated with the CE 418. For example, FIG. 7 showsone example of the global information 314. In the example of FIG. 7, theglobal information 314 is maintained in a table 700 of a database.However, other mechanisms for storing and organizing the globalinformation 314 are applicable as well. FIG. 7 shows that each entry(row) comprises the IP address 702 of a UE device, the unique ID (ifavailable) 704 of the UE device, and the EE identifier 706 of the EE 424where the UE device currently located. It should be noted thatadditional information can be included in the global information 314 aswell. Also, a separate table can be maintained for each EE 424 ascompared to a single table as shown in FIG. 7. In this embodiment, theEE identifier 706 is used to identify the particular table/record inwhich to store the IP address and unique ID of the UE device 408. The EEidentifier 706 is not required to be stored in each row of this tablesince the entire table is associated with the given EE.

When the CE 418 receives UE location information from an EE 424, theupdater 304 at the CE 418 updates the global information 314 basedthereon. For example, the updater 304 analyzes the received locationinformation and identifies either the unique identifier and/or the IPaddress of the UE device 408. The updater 304 then compares the receivedunique identifier and/or the IP address to the global information 314 todetermine if an entry currently exists for the UE device 408. If anentry does not exist this indicates, for example, that the UE device 408has just entered the wireless communication network 102 or has movedfrom an eNodeB without an EE. The updater 304 creates an entry 802 inthe global information 314 for the UE device 408 (and/or EE 424) asshown in FIG. 8. If an entry does exist, this indicates that the UEdevice 408 has moved from one eNodeB 412 with an EE 424 to anothereNodeB 413 with an EE 425. The updater 304 updates the EE information902 in global information 314 for the UE device 408, as shown in FIG. 9.For example, FIG. 7 shows that the UE device with the IP address ofIP_Address_1 device was previously coupled to EE_1, but the UE locationinformation received from an EE 425 indicates that the UE device is nowcoupled to the EE 425. Therefore, the updater 304 updates the globalinformation 314 for the UE device to reflect that it is now located at(coupled to) EE 425 by associating its identifier, EE_2, with the UEdevice.

It should be noted that in an embodiment where separate tables aremaintained for each EE 424, 425, the updater 304 can search through thetables to identify an entry comprising the unique identifier and/or theIP address of the given UE device. Once this entry is identified theupdater 304 can remove this entry from the identified table since the UEis no longer located at the previous EE 424, or the updater 304 can markthis entry as invalid. The updater 304 can then add an entry to thetable associated with the new EE 425 identified in the UE informationreceived from the EE 425 to indicate that the UE device 408 is currentlycoupled to the EE 425.

Once the global UE location manager 122 at the CE 418 identifies the EE424 where the UE device 408 was previously coupled to, the EE notifier306 the notifies this EE 424 that the UE device 408 has been decoupledtherefrom. It should be noted that the CE 418 and EE 425 can use anyTCP/IP based protocol to exchange messages. For example, the protocolmessages can be encoded in a binary format by using remote procedurecalls, or a human readable format by using web services. The local UElocation manager 120 at this EE 424 receives this notification andupdates its local information 214 accordingly. For example, the local UElocation manager 120 removes the entry associated with the UE devicefrom its local information 214. Alternatively, the local UE locationmanager 120 keeps the entry but updates the entry to reflect that the UEdevice is no longer located at the EE 424.

In another embodiment, the local UE location manager 120 at an EE 424can detect when a UE device 408 is no longer located at (coupled to) theEE 424 without receiving a notification from the CE 418. For example,the local UE location manager 120 determines if any IP data packetsassociated with a UE device 408 identified within its local information214 have been received within a given time threshold. The local UElocation manager 120 can store a time stamp within the local information214 associated with the last IP data packet received for the given UEdevice 408. If a new IP data packet is not received within a givenamount of time (threshold) from the stored time stamp the local UElocation manager 120 determines that the UE device 408 has moved to anew EE 425; has left the network; or has moved to an eNodeB 417 that isnot associated with an EE. The local UE location manager 120 updates itslocal information 214 to indicate that the UE device 408 is no longerlocated at the EE 424 and notifies the CE 418. Upon receiving thenotification from the EE 424 that the UE device 408 is no longer locatedat the EE 424, the CE 418 updates its global UE location information 314to indicate that the UE device 408 is no longer located at the EE 424.

In another embodiment, the EEs 424, 425 and CE 418 detect UE mobilityutilizing in-band signaling in the up-link direction as shown in FIG.10. In this embodiment, after a UE device 408 is coupled to an eNodeB413 associated with an EE 425 and establishes an IP link through thewireless communications network 102 the UE device 408 sends a packet1026 to a destination such as a server 406. The local UE locationmanager 120 at the EE 425 intercepts this uplink packet 1026 andperforms one or more mangling operations. For example, the packetmangler 210 of the location manager 120 mangles an uplink packet bymarking unused flags in the IP packet header and also adds the ID of theEE 425 to the header. For example, FIG. 11 shows that the packet mangler210 has marked one or more flags 1104, 1106 within the TCP header 1102of the IP data packet 1100. However, any of the unused fields in the IPheader and/or UDP header of the packet 1100 can also be marked by themangler 210. FIG. 11 also shows that the packet mangler 210 has alsoadded the ID 1110 of the EE to packet in the packet payload 1108 so thatthe CE 418 can determined under which EE the UE 408 has attached to. Itshould be noted that the local UE location manager 120 can also addproprietary TCP options to the IP data packet 1100 to carry the ID ofthe EE 425 and to also indicated that the packet 1100 comprises locationinformation.

The EE 425 sends the mangled uplink packet 1028 to its destination andis intercepted by the CE 418. The packet analyzer 302 of the CE 418analyzes the received packet 1028 and identifies the mangled fieldstherein. For example, the packet analyzer 302 determines that one ormore of the flags are marked indicating that the packet compriseslocation information for the UE device 408 associated with the packet.The packet analyzer 302 identifies the UE device 408 associated with theuplink packet via the source address information within the packet(and/or an identifier associated with the UE device 408 within thepacket) and updates the global information 314 similar to theembodiments discussed above. In addition, the packet demangler 310 ofthe global UE location manager 122 changes the received uplink packet toits original form. For example, the packet demangler 310 unmarks any ofthe marked flags in the packet header and also removes the EE ID fromthe packet as well. The CE 418 then sends the packet 1030 in itsoriginal form to its destination.

Packet mangling can also be used to determine when a UE device 408 hasmoved from an eNodeB 413 associated with an EE 425 to an eNodeB 417 thatis not associated with an EE. For example, when the CE 418intercepts/receives a downlink (e.g., server to UE device communication)IP packet the packet mangler 308 performs one or more manglingoperations. These mangling operations include (but are not limited to)changing the port number within a TCP header of the packet to an unusedport; change the port number within a UDP of the packet to an unusedport; changing the protocol number in the IP header; changing theIP/TCP/UDP checksum value (e.g., by adding 1); etc.

The CE 418 then forwards the received packet to its indicateddestination (i.e., UE device 408). If the eNodeB 412 servicing thedestination UE device 408 is coupled to an EE 425 the local UE locationmanager 124 intercepts the packet and performs one or more demanglingoperations. For example, if the packet demangler 212 the EE 425determines that the packet has been mangled by changing the port numberto an unused port number the packet demangler 212 changes the portnumber back to the original port number. If the packet demangler 212determines that the protocol number has been changed the packetdemangler 212 changes the protocol back the original port number. If thepacket demangler 212 determines that the checksum value has been changedthe packet demangler 212 changes the checksum value back to the originalvalue. The EE 425 then sends the received packet in its original form tothe destination UE device 408.

However, if the UE device 408 is coupled to an eNodeB 417 that is notassociated with an EE the UE device 408 receives the mangled data packetforwarded by the CE 418 and the TCP/IP stack of the UE device 408 sendsa feedback back to the server 406 (e.g., an error response). The CE 418sends the packet to the IP address associated with the UE device 408.The wireless communication network 102 forwards the packet to thelocation where the UE device 408 is attached to. With respect to theerror message sent from the UE device 408 back to the server 406,wireless communication network 102 also guarantees that the packettraverses the P-GW 418. Therefore, the global UE location manager 122can intercept the error message.

For example, the UE device 408 sends a TCP RESET message to the server406 in response to the original port number having been changed in theTCP header. If the original port number in the UDP header was changedthe UE device 408 sends an ICMP ERROR (destination port unreachable)message to the server 406. The UE device 408 also sends an ICMP ERROR(destination protocol unreachable) message to the server 406 in responseto the original protocol being changed in the IP header. In any of theabove cases the CE 418 intercepts the error message generated by the UEdevice 408, which is analyzed by the UE feedback analyzer 312. Based onthis analysis the CE 418 can choose to forward the message to the server406 or block the message. If the original checksum value has beenchanged the UE device 408 discards the packet, which results in atime-out occurring at the previous EE. The previous EE 425 can thennotify the CE 418 that the UE device 408 is no longer located at itsassociated base station. Therefore, when the CE 418 receives one of theerror messages above or the notification from the previous EE 425 thefeedback analyzer 312 determines that the UE device 408 is coupled to abase station that is not associated with an EE. This information can beused, for example, by the CE 418 to determine if byte caching operationsshould be performed on received packets. For example, if the UE device408 is coupled to a base station that is not associated with an EE theCE 418 determines that byte caching operations should not be performed.

As can be seen from the above discussion, the CE and EE work incoordination to detect where a particular user is currently attached.The CE maintains a global view of mobile devices and coordinatesexchange of information between different EE as necessary. Detection ofchange in user mobility is can be performed in various ways. Forexample, a flow can be observed from a mobile device that isstrategically altered by the attached EE positively affirming to the CEthe attachment of the mobile device to a particular EE (and vice versa).In another example, the lack of flow from a previously attached devicecan be observed. This indicates that the device is inactive for anynumber of reasons.

Operational Flow Diagrams

FIG. 12 is an operational flow diagram illustrating one example ofdetecting mobility of UE devices (wireless communication devices) by anedge entity (e.g., CE 118). The operational flow diagram of FIG. 12begins at step 1202 and flows directly to step 1204. The local UElocation manager 120 at an EE 124, at step 1203, analyzes one or moreInternet Protocol (IP) data packets associated with a UE device(wireless communication device) 108, where the UE device 108 is coupledwith the EE 124. The local UE location manager 120, at step 1206,identifies the IP address (or unique ID) associated with the UE devicebased on analyzing the one or more IP data packets.

The local UE location manager 120, at step 1208, compares the IP address(or ID) to the local UE location information 214 maintained by the EE124. The local UE location manager 120, at step 1210, determines if anyof the IP addresses (or IDs) within the local information 214 matchesthe IP address (or ID) obtained from the IP data packets. If the resultof this determination is positive the UE device 108 has been coupledwith the EE 124 for a given amount of time and the control flow returnsto step 1204. If the result of this determination is negative, the localUE location manager 120 determines that the UE device 108 is a newlycoupled device and the EE 124. The local UE location manager 120, atstep 1212, updates the UE location information 214 to indicate that theUE device 108 is currently coupled to the EE 124. The local UE locationmanager 120, at step 1214, notifies the CE 118 that the UE device 108 iscurrently coupled to the EE 124. The control flow returns to step 1204.

FIG. 13 is an operational flow diagram illustrating another example ofdetecting mobility of UE devices by an edge entity (e.g., EE 124). Theoperational flow diagram of FIG. 13 begins at step 1302 and flowsdirectly to step 1304. The local UE location manager 120, at step 1304,monitors for Internet Protocol (IP) data packets associated with a givenUE device 108. The local UE location manager 120, at step 1306,determines that one or more IP data packets associated with the given UEdevice 108 have failed to be received within a given threshold. Thelocal UE location manager 120, at step 1308, updates a set of UElocation information 214 associated with the given UE device 108 toindicate that the given UE device 108 has been decoupled from the EE 124(e.g., the last known EE associated with the UE device 108). The localUE location manager 120, at step 1310, notifies the CE 118 that thegiven UE device 108 has been decoupled from the EE 124. The control flowreturns to step 1304.

FIG. 14 is an operational flow diagram illustrating one example ofdetecting mobility of UE devices by a CE. The operational flow diagramof FIG. 14 begins at step 1402 and flows directly to step 1404. Theglobal UE location manager 122, at step 1404, intercepts one or moreInternet Protocol (IP) data packets associated with a UE device 108,where the UE device 108 is coupled to an EE 124. The global UE locationmanager 122, at step 1406, determines that the one or more IP datapackets have been changed by the EE 124. The global UE location manager122, at step 1408, identifies, based on the determining, at least oneidentifier associated with the EE 124 within the one or more IP datapackets.

The updating global UE location manager 122, at step 1410, updates,based on the at least one identifier, a set of global UE locationinformation 314 to indicate that the wireless communication device iscurrently coupled to the EE 124. The global UE location manager 122, atstep 1412, unmarks the flags in the one or more IP data packets thatwere changed by the EE 124. The global UE location manager 122 alsoremoves the EE identifier from the one or more IP data packets as well.The global UE location manager 122, at step 1414, sends the one or moreIP data packets in their original form to their destination. The controlflow returns to step 1404.

FIG. 15 is an operational flow diagram illustrating another example ofdetecting mobility of UE devices by a CE. The operational flow diagramof FIG. 15 begins at step 1502 and flows directly to step 1504. Theglobal UE location manager 122, at step 1504, intercepts one or moreInternet Protocol (IP) data packets associated with a UE device 108. Theglobal UE location manager 122, at step 1506, changes (mangles) at leastone parameter of the one or more IP data packets. The global UE locationmanager 122, at step 1508, identifies, based on the data packet and/orthe global UE location information 314, the IP address associated withUE device 108.

The global UE location manager 122, at step 1510, sends the one or moreIP data packets that have been changed to the UE device 108 based on theidentified IP address associated therewith. The global UE locationmanager 122, at step 1512, determines if an error message was receivedfrom the UE device 108. If the result of this determination is negative,the global UE location manager 122, at step 1514, determines that the UEdevice 108 is still coupled to an EE. If the result of thisdetermination is positive, the global UE location manager 122 determinesthat the UE device 108 is no longer coupled to an EE. The global UElocation manager 122, at step 1516, updates its global UE locationinformation 314 to indicate that the UE device 108 is no longer coupledto an EE. The control flow returns to step 1504.

Information Processing System

Referring now to FIG. 16, this figure is a block diagram illustrating aninformation processing system that can be utilized in embodiments of thepresent invention. The information processing system 1602 is based upona suitably configured processing system configured to implement one ormore embodiments of the present invention (e.g., the EE 124 or CE 118 ofFIG. 1). Any suitably configured processing system can be used as theinformation processing system 1602 in embodiments of the presentinvention. The components of the information processing system 1602 caninclude, but are not limited to, one or more processors or processingunits 1604, a system memory 1606, and a bus 1608 that couples varioussystem components including the system memory 1606 to the processor1604.

The bus 1608 represents one or more of any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, an accelerated graphics port, and a processor or local bus usingany of a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronics Standards Association (VESA) local bus, andPeripheral Component Interconnects (PCI) bus.

Although not shown in FIG. 16, the main memory 1606 includes the localor global UE location managers 120, 122 and the local or global UElocation information 214, 314. The local or global UE location managers120, 122 can reside within the processor 1604, or be a separate hardwarecomponent. The system memory 1606 can also include computer systemreadable media in the form of volatile memory, such as random accessmemory (RAM) 1610 and/or cache memory 1612. The information processingsystem 1602 can further include other removable/non-removable,volatile/non-volatile computer system storage media. By way of exampleonly, a storage system 1614 can be provided for reading from and writingto a non-removable or removable, non-volatile media such as one or moresolid state disks and/or magnetic media (typically called a “harddrive”). A magnetic disk drive for reading from and writing to aremovable, non-volatile magnetic disk (e.g., a “floppy disk”), and anoptical disk drive for reading from or writing to a removable,non-volatile optical disk such as a CD-ROM, DVD-ROM or other opticalmedia can be provided. In such instances, each can be connected to thebus 1608 by one or more data media interfaces. The memory 1606 caninclude at least one program product having a set of program modulesthat are configured to carry out the functions of an embodiment of thepresent invention.

Program/utility 1616, having a set of program modules 1618, may bestored in memory 1606 by way of example, and not limitation, as well asan operating system, one or more application programs, other programmodules, and program data. Each of the operating system, one or moreapplication programs, other program modules, and program data or somecombination thereof, may include an implementation of a networkingenvironment. Program modules 1618 generally carry out the functionsand/or methodologies of embodiments of the present invention.

The information processing system 1602 can also communicate with one ormore external devices 1620 such as a keyboard, a pointing device, adisplay 1622, etc.; one or more devices that enable a user to interactwith the information processing system 1602; and/or any devices (e.g.,network card, modem, etc.) that enable computer system/server 1602 tocommunicate with one or more other computing devices. Such communicationcan occur via I/O interfaces 1624. Still yet, the information processingsystem 1602 can communicate with one or more networks such as a localarea network (LAN), a general wide area network (WAN), and/or a publicnetwork (e.g., the Internet) via network adapter 1626. As depicted, thenetwork adapter 1626 communicates with the other components ofinformation processing system 1602 via the bus 1608. Other hardwareand/or software components can also be used in conjunction with theinformation processing system 1602. Examples include, but are notlimited to: microcode, device drivers, redundant processing units,external disk drive arrays, RAID systems, tape drives, and data archivalstorage systems.

Non-Limiting Examples

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method, or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention have been discussed above withreference to flowchart illustrations and/or block diagrams of methods,apparatus (systems) and computer program products according to variousembodiments of the invention. It will be understood that each block ofthe flowchart illustrations and/or block diagrams, and combinations ofblocks in the flowchart illustrations and/or block diagrams, can beimplemented by computer program instructions. These computer programinstructions may be provided to a processor of a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor of the computer or other programmabledata processing apparatus, create means for implementing thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The description of the present invention has been presented for purposesof illustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. An edge entity disposed at an edge of a wirelesscommunication network for detecting mobility of wireless communicationdevices, the edge entity comprising: a memory; a processorcommunicatively coupled to the memory, the processor monitoring forInternet Protocol (IP) data packets associated with a given wirelesscommunication device; determining that one or more IP data packetsassociated with the given wireless communication device have failed tobe received within a given time threshold; and updating, based ondetermining that one or more IP data packets associated with the givenwireless communication device have failed to be received within a giventime threshold, a local set of wireless communication device locationinformation associated with the given wireless communication device toindicate that the given wireless communication device has been decoupledfrom the edge entity, the local set of wireless communication devicelocation information being stored at the edge entity.
 2. The edge entityof claim 1, the processor further: notifying a central entity disposedwithin the wireless communication network that the wirelesscommunication device has been decoupled from the edge entity.
 3. Theedge entity of claim 2, wherein the central entity is an informationprocessing system that monitors data traffic in the wirelesscommunication network.
 4. The edge entity of claim 2, wherein thecentral entity is situated between a packet gateway node and the leastone information processing system.
 5. The edge entity of claim 1,wherein a base station within the wireless communication networkcomprises the edge entity.
 6. A central entity disposed within awireless communication network for detecting mobility of wirelesscommunication devices, the central entity comprising: a memory; aprocessor communicatively coupled to the memory, the processorintercepting one or more Internet Protocol (IP) data packets associatedwith a wireless communication device, wherein the central entity issituated within the wireless communication network between the edgeentity and the information processing system; determining that the oneor more IP data packets have been changed by the edge entity;identifying, based on the determining and data within the one or more IPdata packet, at least one identifier associated with the edge entitywithin the one or more IP data packets; and updating, based on the atleast one identifier, a set of wireless communication device locationinformation, wherein the updating indicates that the wirelesscommunication device is currently coupled to the edge entity.
 7. Thecentral entity of claim 6, wherein the determining comprises: analyzingthe one or more IP data packets; and determining, based on theanalyzing, that one or more flags in at least one header of the one ormore data packets has been marked.
 8. The central entity of claim 6, theprocessor further: determining that one or more flags in at least oneheader of the one or more data packets has been marked; and unmarkingthe one or more flags.
 9. The central entity of claim 8, the processorfurther: removing the at least one identifier from the one or more IPdata packets.
 10. The central entity of claim 9, the processor further:sending, after the unmarking and the removing, the one or more IP datapackets to a destination associated therewith.
 11. A central entitydisposed within a wireless communication network for detecting mobilityof wireless communication devices, the central entity comprising: amemory; a processor communicatively coupled to the memory, the processorintercepting, by the central entity, one or more Internet Protocol (IP)data packets associated with a wireless communication device, whereinthe central entity is situated within the wireless communication networkbetween an edge entity coupled to the wireless communication device andthe information processing system; changing, by the central entity, atleast one parameter of the one or more IP data packets; identifying, bythe central entity, an IP address associated with the wirelesscommunication device; sending, by the central entity, the one or more IPdata packets that have been changed to the wireless communication devicebased on the IP address that has been identified; based on detectingthat the wireless communication device has sent an error message inresponse to the IP data packets that have been changed, determining, bythe central entity, that the wireless communication device is currentlydecoupled from an edge entity; and based on detecting an absence oferror message being sent from the wireless communication device inresponse to the IP data packets that have been changed, determining, bythe central entity, that the wireless communication device is currentlycoupled to an edge entity.
 12. The central entity of claim 11, theprocessor further: updating a set of wireless communication devicelocation information to indicate that the wireless communication deviceis currently decoupled from an edge entity.
 13. The central entity ofclaim 11, wherein changing at least one parameter of the one or more IPdata packets comprises one of: changing a port number of a TransmissionControl Protocol header to an unused port; changing a port number of aUser Datagram Protocol header to an unused port; changing a protocolnumber in an IP header; and changing a checksum value in a header of theone or more IP data packets.